<!DOCTYPE html>
<html lang="en">
<head>
	<meta charset="UTF-8">
	<meta http-equiv="X-UA-Compatible" content="IE=edge">
    <meta name="viewport" content="width=device-width, initial-scale=1">
	<title>Upgrading clusters | ElasticSearch 7.7 权威指南中文版</title>
	<meta name="keywords" content="ElasticSearch 权威指南中文版, elasticsearch 7, es7, 实时数据分析，实时数据检索" />
    <meta name="description" content="ElasticSearch 权威指南中文版, elasticsearch 7, es7, 实时数据分析，实时数据检索" />
    <!-- Give IE8 a fighting chance -->
    <!--[if lt IE 9]>
    <script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js"></script>
    <script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script>
    <![endif]-->
	<link rel="stylesheet" type="text/css" href="../static/styles.css" />
	<script>
	var _link = 'ccr-upgrading.html';
    </script>
</head>
<body>
<div class="main-container">
    <section id="content">
        <div class="content-wrapper">
            <section id="guide" lang="zh_cn">
                <div class="container">
                    <div class="row">
                        <div class="col-xs-12 col-sm-8 col-md-8 guide-section">
                            <div style="color:gray; word-break: break-all; font-size:12px;">原英文版地址: <a href="https://www.elastic.co/guide/en/elasticsearch/reference/7.7/ccr-upgrading.html" rel="nofollow" target="_blank">https://www.elastic.co/guide/en/elasticsearch/reference/7.7/ccr-upgrading.html</a>, 原文档版权归 www.elastic.co 所有<br/>本地英文版地址: <a href="../en/ccr-upgrading.html" rel="nofollow" target="_blank">../en/ccr-upgrading.html</a></div>
                        <!-- start body -->
                  <div class="page_header">
<strong>重要</strong>: 此版本不会发布额外的bug修复或文档更新。最新信息请参考 <a href="https://www.elastic.co/guide/en/elasticsearch/reference/current/index.html" rel="nofollow">当前版本文档</a>。
</div>
<div id="content">
<div class="breadcrumbs">
<span class="breadcrumb-link"><a href="index.html">Elasticsearch Guide [7.7]</a></span>
»
<span class="breadcrumb-link"><a href="high-availability.html">Set up a cluster for high availability</a></span>
»
<span class="breadcrumb-link"><a href="xpack-ccr.html">Cross-cluster replication</a></span>
»
<span class="breadcrumb-node">Upgrading clusters</span>
</div>
<div class="navheader">
<span class="prev">
<a href="remote-recovery.html">« Remote recovery</a>
</span>
<span class="next">
<a href="snapshot-restore.html">Snapshot and restore »</a>
</span>
</div>
<div class="section xpack">
<div class="titlepage"><div><div>
<h2 class="title">
<a id="ccr-upgrading"></a>Upgrading clusters<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/elasticsearch/edit/7.7/docs/reference/ccr/upgrading.asciidoc">edit</a><a class="xpack_tag" href="https://www.elastic.co/subscriptions"></a>
</h2>
</div></div></div>
<p>Clusters that are actively using cross-cluster replication require a careful approach to upgrades.
Otherwise index following may fail during a rolling upgrade, because of the
following reasons:</p>
<div class="ulist itemizedlist">
<ul class="itemizedlist">
<li class="listitem">
If a new index setting or mapping type is replicated from an upgraded cluster
to a non-upgraded cluster then the non-upgraded cluster will reject that and
will fail index following.
</li>
<li class="listitem">
Lucene is not forwards compatible and when index following is falling back to
file based recovery then a node in a non-upgraded cluster will reject index
files from a newer Lucene version compared to what it is using.
</li>
</ul>
</div>
<p>Rolling upgrading clusters with cross-cluster replication is different in case of uni-directional
index following and bi-directional index following.</p>
<div class="section">
<div class="titlepage"><div><div>
<h3 class="title">
<a id="_uni_directional_index_following"></a>Uni-directional index following<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/elasticsearch/edit/7.7/docs/reference/ccr/upgrading.asciidoc">edit</a>
</h3>
</div></div></div>
<p>In a uni-directional setup between two clusters, one cluster contains only
leader indices, and the other cluster contains only follower indices following
indices in the first cluster.</p>
<p>In this setup, the cluster with follower indices should be upgraded
first and the cluster with leader indices should be upgraded last.
If clusters are upgraded in this order then index following can continue
during the upgrade without downtime.</p>
<p>Note that a chain index following setup can also be upgraded in this way.
For example if there is a cluster A that contains all leader indices,
cluster B that follows indices in cluster A and cluster C that follows
indices in cluster B. In this case the cluster C should be upgraded first,
then cluster B and finally cluster A.</p>
</div>

<div class="section">
<div class="titlepage"><div><div>
<h3 class="title">
<a id="_bi_directional_index_following"></a>Bi-directional index following<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/elasticsearch/edit/7.7/docs/reference/ccr/upgrading.asciidoc">edit</a>
</h3>
</div></div></div>
<p>In a bi-directional setup between two clusters, each cluster contains both
leader and follower indices.</p>
<p>When upgrading clusters in this setup, all index following needs to be paused
using the <a href="ccr-post-pause-follow.html" class="ulink" target="_top">pause follower API</a> and the
 <a href="ccr-pause-auto-follow-pattern.html" class="ulink" target="_top">pause auto-follower API</a> prior to
upgrading both clusters. After both clusters have been upgraded then index
following can be resumed using the
<a href="ccr-post-resume-follow.html" class="ulink" target="_top">resume follower API</a>].</p>
</div>

</div>
<div class="navfooter">
<span class="prev">
<a href="remote-recovery.html">« Remote recovery</a>
</span>
<span class="next">
<a href="snapshot-restore.html">Snapshot and restore »</a>
</span>
</div>
</div>

                  <!-- end body -->
                        </div>
                        <div class="col-xs-12 col-sm-4 col-md-4" id="right_col">
                        
                        </div>
                    </div>
                </div>
            </section>
        </div>
    </section>
</div>
<script src="../static/cn.js"></script>
</body>
</html>